-
Notifications
You must be signed in to change notification settings - Fork 47.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove ES3-specific transforms #12716
Conversation
ReactDOM: size: -0.4%, gzip: -0.2% Details of bundled changes.Comparing: 045d4f1...52209cc react-dom
react-art
react-test-renderer
react-reconciler
react-native-renderer
Generated by 🚫 dangerJS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, if our concern is the name return
being used as Fiber property – we should probably just use a different name internally. That's a bigger change though, but if there's a significant perf loss from this, then we should look more into it.
I don't think it's the name specifically that's the issue—just the fact that it turns dot-access into quotes because of legacy browsers we don't care about anymore. |
The goal of this change isn't to fix that specifically, it's just that these transforms aren't useful now and can be removed. |
Should /~https://github.com/facebook/react/blob/master/package.json#L34 |
Oh yeah, send a PR please? |
We stopped supporting IE8 a long time ago.
As far as I can tell all other major browsers support reserved property names.
By dropping these transforms we ensure the bundles contain
fiber.return
rather thanfiber["return"]
which I'm worried might deopt.I've seen
["return"]
being "hot" in some line-by-line Chrome traces before.